feat(helm): add namespaceOverride support to FluentBit chart#1919
Merged
cw-Guo merged 1 commit intofluent:masterfrom Apr 13, 2026
Merged
Conversation
Adds fluentbit.namespaceOverride value so users can deploy FluentBit resources into a namespace different from .Release.Namespace. Fixes fluent#1918 Signed-off-by: shawn.mulford <[email protected]>
cw-Guo
approved these changes
Apr 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
fluentbit.namespaceOverrideto allow deploying FluentBit resources into a configurable namespace, falling back to.Release.Namespacewhen unset.Changes
values.yaml: addedfluentbit.namespaceOverride: ""templates/fluentbit-fluentBit.yaml: namespace resolves viadefault .Release.Namespace .Values.fluentbit.namespaceOverrideFixes #1918